Encrypted group communications

ABSTRACT

Secure data transfers between communication nodes is performed using a group encryption key supplied by a remote management system. A first node transmits a request for secure communications with a second node to the remote management system using a control channel. The remote management system generates and encrypts a group encryption key usable by the first and second nodes and forwards the encrypted group encryption key to the first and second nodes using one or more control channels. The first and second communication nodes decrypt the group encryption key and use it to encrypt data transmitted between the nodes using a data transport network. In some implementations the securely communicating nodes may use encryption keys and/or techniques that prevent the remote management system from eavesdropping on the nodes&#39; communications.

RELATED APPLICATIONS

This application hereby claims the benefit of and priority to U.S.Provisional Patent Application 62/236,534, entitled “ENCRYPTED GROUPCOMMUNICATION DEVICES WITH SIDE CHANNEL KEYS,” filed 2 Oct. 2015, andwhich is hereby incorporated by reference in its entirety (including anyappendices thereto).

TECHNICAL FIELD

Aspects of the disclosure are related to the field of communicationsand, in particular, to secure communications for group communications.

TECHNICAL BACKGROUND

Various communication devices can be employed to facilitatecommunication between users. These devices can include cellulartelephones, smartphones, discrete devices, computers, and tablets, amongothers, which provide an efficient way for users to communicate withoutbeing in the same physical location. These devices may be groupedtogether to facilitate communications among some but not all of thedevices on a network. When devices within a group wish to transmitsensitive information over public links to one another, they need to beable to encrypt the information quickly, easily and securely so that theinformation can be read (or otherwise used) only by authorizedrecipients.

OVERVIEW

Secure data transfers between communication nodes (e.g., members of acommunication node group) can be performed using a group encryption keysupplied by a remote management system or the like. A firstcommunication node transmits a request to the remote management systemusing a control channel or other management link, asking for securecommunications with one or more additional communication nodes (e.g., asecond communication node). The request can include identity data thatallows the remote management system to generate a group encryption keyusable by the first communication node and any additional communicationnodes to which the request applies. The remote management system mayencrypt the group encryption key and forward the encrypted groupencryption key using one or more control channels to the firstcommunication node and second communication node. The first and secondcommunication nodes decrypt the group encryption key and use it toencrypt data transmitted between the nodes using a data transportnetwork (e.g., including a transport server and one or more datatransport links). In some implementations the securely communicatingnodes may use encryption keys and/or techniques that prevent the remotemanagement system from eavesdropping on the nodes' communications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a communication system.

FIG. 2 illustrates a communication system.

FIG. 3 illustrates a communication system.

FIG. 4 illustrates a remote management system.

FIG. 5A illustrates a method for operating a remote management system.

FIG. 5B illustrates a method for operating a remote management system.

FIG. 6 illustrates a communication node.

DETAILED DESCRIPTION

The non-limiting examples below discuss personal communication nodesthat allow group communication sessions among various authorized users(e.g., members of the group). These personal communication nodes caninclude discrete devices (e.g., wearable communication devices)specialized for group communications that include one or more wirelesstransceivers and user interface elements tailored to streamline groupcommunications. The group communications can be initiated and altered(e.g., by user intervention and/or automatically by a shared remotemanagement system which can respond to one or more dynamic factors toform or change groups or group status). In some examples, one or morefeatures of the discrete devices can be incorporated into other devices,such as personal communication devices which comprise cellularsmartphones, gaming devices, personal computers, tablet computers, andthe like. Voice command features can be included that comprise groupforming and alteration features, keyword-based searching, productivityassistance, or navigation assistance, among other features. Furtherfeatures can include conversational interaction for informationtransmittal or retrieval, such as activity reminders, weather, stocks,messaging, email, calendar, contacts, notes, music, clocks, webbrowsers, maps and other applications.

When these various devices stream or otherwise transfer data betweeneach other, sensitive data needs to be encrypted to prevent unauthorizedaccess. When two different nodes wish to transfer sensitive data theymay contact a remote management system that generates encryption keysfor the nodes and provides the keys to the nodes using channels separatefrom the transport channels used to transfer the data.

In a first non-limiting example, FIG. 1 illustrates communication system100, which can be employed to provide encryption features for datatransfers between communication nodes 102 and 103. System 100 includescommunication nodes 102 and 103, and remote management system 120.

Communication nodes 102 and 103 may each comprise one or moretransceivers, audio transducers, processing systems, communicationinterfaces, environmental sensors, accelerometers, gyroscopes, GlobalPositioning System (GPS) receivers, user interfaces, and other systems.Remote management system 120 may comprise a computing system comprisingone or more computing devices capable of managing services to aplurality of communication nodes, such as communication nodes 102 and103.

Communication nodes 102 and 103 communicate with remote managementsystem 120 over associated ones of management links 141 and 142, whichcan comprise one or more network links and which can function as controlchannels (and are referred to as such) in this and other examples.Management links 141 and 142 can each comprise one or more wirelesslinks that can each further include Long Term Evolution (LTE), GlobalSystem For Mobile Communications (GSM), Code Division Multiple Access(CDMA), IEEE 802.11 WiFi, Bluetooth, Personal Area Networks (PANs), WideArea Networks, (WANs), Local Area Networks (LANs), or Wireless LocalArea Networks (WLANs), including combinations, variations, andimprovements thereof. These links can carry any communication protocolsuitable for wireless communications, such as Internet Protocol (IP) orEthernet.

Additionally, management links 141 and 142 can include one or more wiredportions which can comprise synchronous optical networking (SONET),hybrid fiber-coax (HFC), Time Division Multiplex (TDM), asynchronoustransfer mode (ATM), circuit-switched, communication signaling, or someother communication signaling, including combinations, variations orimprovements thereof. Management links 141 and 142 can each use metal,glass, optical, air, space, or some other material as the transportmedia. Management links 141 and 142 may each be a direct link, or mayinclude intermediate networks, systems, or devices, and may include alogical network link transported over multiple physical links.

In the non-limiting example of FIG. 1, each communication node 102 and103 monitors one or more attributes (e.g., from associated positionalsensors, audio transducers, GPS receivers, accelerometers, wirelesstransceivers, environmental sensors, or other sensors or devices capableof monitoring the attributes discussed herein). These attributescomprise data or information that may be used for dynamically formingand changing node groups, as well as for intelligent agent features forcommunication nodes 102 and 103. For example, one or more of the soundlevel of an environment, user preferences, proximity of one personalcommunication node to another, location, communication status, identity,and traveling speed may be attributes used for dynamically forming andchanging groups of nodes as well as for intelligent agent features fornodes 102 and 103.

Communication nodes 102 and 103 periodically transfer messages fordelivery to remote management system 120 (e.g., indicating dynamicchanges in one or more attributes, user inputs, and/or other data usefulin managing a node or a node group). Communication nodes 102 and 103 maytransfer a message to remote management system 120 whenever an attributechanges and/or at periodic intervals. Remote management system 120 canuse dynamic changes in one or more attributes to form, modify and/orterminate groups of communication nodes 102 and 103, and for intelligentagent features for communication nodes 102 and 103. Although remotemanagement system 120 and nodes 102 and 103 are each shown as separateentities in FIG. 1, it should be understood that features of remotemanagement system 120 can be included in one or more of personalcommunication nodes 102 and 103.

A communication node may use one or more secure communication methodsfor communicating with members of a communication group, withnon-members and/or with a remote management system or the like. Securecommunication methods include systems, techniques, protocols, methodsand other approaches enabling users and nodes to securely sharecommunications and other information with one another withoutinterception or monitoring of the information or associatedcommunications by non-members and/or an unauthorized third-party. Securecommunication methods may comprise symmetric key encryption, asymmetrickey encryption, public-key encryption, or some other type of encryption,including combinations thereof. The actual communications betweenpersonal communication nodes can employ secure communication methods,and the associated links can employ secure communication methodsindependently.

End to end encryption of communications, such as audio communications,can be established among members of the group. These end-to-endencrypted communications can include transport layer security (TLS) orsecure sockets layer (SSL) communications, among other secure linktypes. For example, a secure communication session can be establishedbetween nodes 102 and 103.

In such an example, when node 102 wishes to securely communicate withnode 103 through transport channels 131 and 132 and through network 110,node 102 sends a request for encryption keys through control channel 141to remote management system 120. Remote management system 120 thengenerates keys for nodes 102 and 103 to use in securely communicatingthrough network 110 and transport channels 131 and 132.

Communication nodes 102 and 103 communicate with each other or withother communication nodes or intelligent agents over associated links131 and 132 (and, in this non-limiting example, over network 110).Communication links 131 and 132 can be used to connect communicationnodes 102 and 103 to each other and/or to other personal communicationnodes. In some examples, links 131 and 132 may comprise a mesh networkamong communication nodes 102 and 103, and other nodes. Furthermore,links 131 and 132 can comprise Bluetooth, IEEE 802.11 WiFi, infrared,ultrasonic, or any wireless communication format including combinations,variations or improvements thereof. Communication links 131 and 132 caneach use air or space as the transport media.

FIG. 2 illustrates a non-limiting example of communication system 200,which shares some similarities with communication system 100 shown inFIG. 1. In this example, node 102 sends data securely to node 103 (andpossibly other nodes), which includes intermediately storing the data instorage system 212 within network 210 (e.g., a cloud storage device).

In this non-limiting example, node 102 sends a request for one or moreencryption keys to remote management system 120 over control channel 141(communications over control channel 141 may be made secure in anappropriate manner). In response, remote management system 120 sends therequested encryption key(s) to node 102 over control channel 141 and oneor more corresponding decryption keys to node 103 over control channel142 (again, as with control channel 141, communications over controlchannel 142 may be made secure). Node 102 encrypts the data using anencryption key obtained from remote management system 120 and transfersthe encrypted data to storage system 212 over transport channel 231(e.g., using one or more transport servers that temporarily hold data intransit between nodes, which act as endpoints in system 200). Node 103then transfers the encrypted data from storage system 212 over transportchannel 232 and decrypts the data using the appropriate decryption keyobtained from remote management system 120.

FIG. 3 illustrates communication system 300, which shares somesimilarities with communication system 200 in FIG. 2, and which furtherillustrates details in communication nodes 310 and 320. In thisnon-limiting example, node 310 is a member of various node groups, as isnode 320, though nodes 310 and 320 may not be members of the same groupin some instances. Node 310 includes storage system 311 which storesdevice key 312, group key 313, group key 314, and group key 315. Node320 includes storage system 321 which stores device key 322, group key313, group key 334, and group key 345. In some implementations groupkeys can be used in symmetric encryption and decryption ofcommunications between nodes.

In the non-limiting example of FIG. 3, device keys 312 and 322 may beprogrammed or otherwise incorporated into nodes 310 and 320 atmanufacture. Remote management system 350 can also maintain copies ofall of the device keys for the various nodes associated with and/orserviced by system 350 in some implementations. In this case, node 310and node 320 wish to communicate securely. Node 310 sends a request toremote management system 350 over control channel 381 (step (A)) for agroup key to use in communicating with node 320 along with identity datafor node 310 (e.g., device key 312). Alternatively, node 320 may sendthe request for a group key to remote management system 350 over controlchannel 382 (step (A′)).

In some implementations remote management system 350 can determine thedevice key 312 for node 310 (e.g., if it is not previously programmedinto node 310 and/or transmitted to remote management system 350 by node310) based on the identity data transferred from node 310. Remotemanagement system 350 generates group key 313 (step (B)) for nodes 310and 320 to use to communicate securely with one another. Remotemanagement system 350 encrypts group key 313 (step (C)) (e.g., withdevice key 312 or another key corresponding to the device identity ofnode 310) and transfers the encrypted key (step (D)) to node 310 overcontrol channel 391. System 350 can also then encrypts group key 313(e.g., with device key 322 or another key corresponding to the deviceidentity of node 320) and transfer the encrypted group key 313 to node320 (step (D)) over control channel 392. The transferred group key isdecrypted by node 310 and then used to encrypt user data (step (E)). Theencrypted user data can then be transmitted from node 310 to node 320using data transport links 371, 372 and data transport network 360 (step(F)). The data may be sent in a stream including a header, encryptedblock(s), and an end of stream marker. The transport network can managevarious streams using stream identifiers that ensure streams aredelivered only to appropriate receiving nodes.

Instead of receiving device key 312 or determining device key 312 fromthe identity of node 310, remote management system 350 may negotiate anephemeral device key 312 with node 310 over control channels 381 and 391(e.g., using a cryptographic key exchange algorithm, such asDiffie-Hellman, ElGamal, or other secure key exchange algorithm) By thismethod device key 312 can be used by both remote management system 350and node 310, but is never transmitted over a network, nor stored on astorage device.

Moreover, in this way, no unencrypted keys are transferred over anychannel (including control channels). Once nodes 310 and 320 have groupkey 313, they may use group key 313 to encode and decode communicationsbetween them over transport channels 371 and 372 through network 360(e.g., using a transport server).

Where a remote management system 350 provides instructions to multiplecommunications nodes regarding the formation, modification, and removalof groups, the users of those nodes may wish to keep theircommunications private from a third-party operator of the remotemanagement system 350. In such implementations communication nodes, suchas communication nodes 310 and 320, may exchange secure communicationsto the exclusion of potential eavesdropping by a remote managementsystem 350.

In these types of situations, the device keys 312, 322, etc. ofcorresponding nodes 310, 320, etc. may be cryptographically-secureasymmetric key pairs (e.g., each of which comprises a private device key312A and a public device key 312B and so on). The computation of theasymmetric key pairs may be accomplished with PKCS #1, Elliptic Curvecryptography, or other asymmetric cryptographic techniques, algorithms,etc. These device keys can be provisioned on the communications nodesbefore the initiation of inter-nodal communications, such that theprivate device key 312A is known only to node 310, and is not known tothe remote management system 350, nor to any of the other communicationsnodes. By contrast, public device keys 312B, 322B, and so on, are meantto be known to all parties (e.g., shared with the remote managementsystem 350 and with all communication nodes via control channels 381,391, 382, 392, etc.).

Communications from node 310 to node 320 may be kept private from remotemanagement service 350 by generating group key 313 on node 310, and thenencrypting group key 313 for the use of node 320 using its public devicekey 322B. Node 310 then transmits the encrypted group key 313A to node320 via the remote management system 350 over control channels 381 and392.

Note that remote management system 350 cannot discover the group key 313from the encrypted group key 313 as it does not possess the private key322A. As a consequence, even if the operator of the remote managementsystem 350 can observe transport channels 371 or 372, or any part of thenetwork 360, it cannot decrypt any communications sent by node 310 tonode 320, or vice versa, because it lacks and cannot obtain group key313.

This method may be extended to groups of communications nodes of anysize, through multiple pairwise asymmetric encryption of group keys 313,314, etc. using public device keys 312B, 322B, and so on.

A further refinement of this example allows node 310 to authenticate thepublic device key 322B belonging to node 320. A group of communicationsnodes may have access to a public certification key 351B, which may beprovisioned on each node at the time of manufacture or before the startof inter-nodal communications. Prior to the delivery of the publicdevice key 322B to node 310, public device key 322B may becryptographically signed by a certifying authority in possession of theprivate certification key 351A which is the private key in the key pairincluding public certification key 351B. The cryptographic signature maybe generated using Digital Signature Algorithm (DSA), Elliptic CurveDSA, or any other asymmetric cryptographic signature algorithm. In thismanner, node 310 may use the cryptographic signature algorithm toauthenticate the public key 322B, even if it was provided by an unknownand/or untrusted remote management system 350.

FIG. 4 illustrates one or more implementations of a remote managementsystem 400. Computing system 400 is a non-limiting example (e.g., of acomputing environment that can execute features of remote managementsystem 120 of FIG. 1 and/or remote management system 350 of FIG. 3).Furthermore, elements of remote management system 400 can be distributedover one or more computing devices (including one or more communicationnodes). Remote management system 400 includes processing circuitry 401,storage system 402, software 403, communication interface system 407,and user interface system 408.

It may be understood that remote management system 400 is generallyintended to represent one or more computing systems on which software403 may be deployed and executed (e.g., in order to implement remotemanagement system(s) 120 and/or 350). However, remote management system400 may also be suitable as any computing system on which software 403may be staged and from where one or both may be distributed,transported, downloaded, or otherwise provided to yet another computingsystem for deployment and execution, or yet additional distribution.

Communication interface system 407 may include communication connectionsand devices that allow for communication with other computing systemsover a communication network. Examples of connections and devices thattogether allow for inter-system communication may include networkinterface cards, antennas, power amplifiers, RF circuitry, transceivers,and other communication circuitry. The connections and devices maycommunicate over communication media to exchange communications withother computing systems or networks of systems, such as metal, glass,air, or any other suitable communication media.

User interface system 408 may include a keyboard, a mouse, a voice inputdevice, a touch input device for receiving a touch gesture from a user,a motion input device for detecting non-touch gestures and other motionsby a user, and other comparable input devices and associated processingelements capable of receiving user input from a user. Output devicessuch as a display, speakers, haptic devices, and other types of outputdevices may also be included in user interface system 408. In somecases, the input and output devices may be combined in a single device,such as a display capable of displaying images and receiving touchgestures.

User interface system 408 may also include associated user interfacesoftware executable by processing circuitry 401 in support of thevarious user input and output devices discussed above. Separately or inconjunction with each other and other hardware and software elements,the user interface software and user interface devices may support agraphical user interface, a natural user interface, or any other type ofuser interface. In addition, user input made with respect to the userinterfaces may be input via user interface system 408.

Communication between remote management system 400 and any othercomputing system may occur over a communication network or networks andin accordance with various communication protocols, combinations ofprotocols, or variations thereof. Examples of such communicationnetworks include intranets, internets, the Internet, local areanetworks, wide area networks, wireless networks, wired networks, virtualnetworks, software defined networks, data center buses, computingbackplanes, or any other type of network, combination of network, orvariation thereof. Some communication protocols that may be usedinclude, but are not limited to, the Internet protocol (IP, IPv4, IPv6),the transmission control protocol (TCP), and the user datagram protocol(UDP), as well as any other suitable communication protocol, variation,or combination thereof.

Processing circuitry 401 can comprise one or more microprocessors andother processing circuitry that retrieves and executes software 403 fromstorage system 402. Processing circuitry 401 can be implemented within asingle processing device but can also be distributed across multipleprocessing devices or sub-systems that cooperate in executing programinstructions. Examples of processing circuitry 401 include generalpurpose central processing units, application specific processors, andlogic devices, as well as any other type of processing device,combinations, or variations thereof. In some examples, portions ofprocessing circuitry 401 is separate physically from some elements ofremote management system 400 and area included in remote servers,cloud-based processing systems, or virtualized computing systems.

Storage system 402 can comprise any non-transitory computer readablestorage media capable of storing software 403 that is executable byprocessing circuitry 401. Storage system 402 can also include variousdata structures which comprise one or more databases, tables, lists, orother data structures. Storage system 402 can include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Storagesystem 402 can be implemented as a single storage device but can also beimplemented across multiple storage devices or sub-systems co-located ordistributed relative to each other. Storage system 402 can compriseadditional elements, such as a controller, capable of communicating withprocessing circuitry 401. Examples of storage media include randomaccess memory, read only memory, magnetic disks, optical disks, flashmemory, virtual memory and non-virtual memory, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand that can be accessed by an instruction execution system, as well asany combination or variation thereof.

Software 403 can be implemented in program instructions and among otherfunctions can, when executed by remote management system 400 in generalor processing circuitry 401 in particular, direct remote managementsystem 400, or processing circuitry 401 to operate as described hereinfor a remote management system or other functional systems. Software 403can include additional processes, programs, or components, such asoperating system software, database software, or application software.Software 403 can also comprise firmware or some other form ofmachine-readable processing instructions executable by elements ofprocessing circuitry 401.

In at least one implementation, the program instructions can includeattributes module 404, connection module 405, and encryption module 406.Attributes module 404 can monitor one or more attributes of personalcommunication nodes (e.g., transferring messages for delivery to amanagement system indicating dynamic changes in one or more attributes).These attributes and dynamic changes in attributes can be used to formand change dynamic communication groups among personal communicationnodes and intelligent agent nodes. Attributes module 404 mayperiodically or continuously monitor attributes associated with personalcommunication node sensors or personal communication nodes may sendmessaging or alerts to attributes module 404 when changes are detected.Attributes module 404 receives attributes (e.g., from communicationnodes 102 and 103), and transmits attributes (e.g., to communicationnodes 102 and 103 over control channels such as communication links 141and 142 in FIG. 1).

Connection module 405 can monitor numerous attributes of the variouscommunication nodes 102 and 103, and based on those attributesautomatically forms and modifies groups. Connection module 405 (orelsewhere in storage system 402) may contain a list of pre-configuredgroup parameters that may be used to automatically form pre-configuredgroups when tokens are received from two or more communication nodes.Connection module 405 also provides group formation and modificationfunctionality to a master node enabling it to create and modify groupsof slave nodes. Connection module 405 also may open, control, modify,close, etc. control channels between an remote management system and oneor more communication nodes, for example working via communicationinterface system 407.

Encryption module 406 receives data (e.g., requests for keys fromcommunication nodes such as nodes 102 and 103 of FIG. 1 and/or nodes 310and 320 of FIG. 3) and generates encryption keys (e.g., for transfer tothe nodes over control channels). In some non-limiting examples,encryption module 406 (or elsewhere in storage system 402) containsdevice keys for the various communication nodes that may be indexed bycommunication node identity. This key data must be kept physically andelectronically secure from outside access since it can be used toencrypt keys that are then transferred over control channels to variouscommunication nodes. Encryption module 406 may also use securecryptographic key exchange algorithms (e.g., to negotiate ephemeralencryption keys with nodes 102 and 103 and/or nodes 310 and 320, whichare never stored in the storage system 402).

In general, software 403 can, when loaded into processing circuitry 401and executed, transform processing circuitry 401 overall from ageneral-purpose computing system into a special-purpose computing systemcustomized to operate as described herein for a remote managementsystem, among other operations. Encoding software 403 on storage system402 can transform the physical structure of storage system 402. Thespecific transformation of the physical structure can depend on variousfactors in different implementations of this description. Examples ofsuch factors can include, but are not limited to the technology used toimplement the storage media of storage system 402 and whether thecomputer-storage media are characterized as primary or secondarystorage. For example, if the computer-storage media are implemented assemiconductor-based memory, software 403 can transform the physicalstate of the semiconductor memory when the program is encoded therein.For example, software 403 can transform the state of transistors,capacitors, or other discrete circuit elements constituting thesemiconductor memory. A similar transformation can occur with respect tomagnetic or optical media. Other physical media transformations arepossible without departing from the scope of the present description,with the foregoing examples provided only to facilitate this discussion.

FIG. 5A illustrates a method for operating a remote management system(e.g., remote management system(s) 120 and/or 350, as illustrated in theFigures). The remote management system may receive a request from afirst communication node for secure communication with a secondcommunication node (operation 500). The request may also identify acommunication node group that remote management system manages. Byidentifying the communication group, the remote management system canthen identify the group's constituent nodes and make sure that keysand/or other information is distributed to the communication nodesrelating to the request. The remote management system generates a groupencryption key for the first and second communication nodes (operation502). FIG. 5B illustrates a method for operating a first communicationnode (e.g., nodes 102, 103, 310, 320 of the Figures) and enabling itssecure communications with a second communication node or other entity.The first communication node transmits a request (operation 510) to aremote management system or the like, requesting secure communicationswith the second communication node (e.g., a node in a communicationgroup managed by the remote management system). The request can be forsecure communications with more than one other communication node insome implementations. The first communication node receives a groupencryption key (operation 512) and, if the received key is encrypted,then decrypts the group encryption key. The first communication nodeencrypts data (e.g., user data, streaming data, voice communicationdata) using the group encryption key (operation 514). The encrypted datais then transmitted (operation 516) to the second communication nodeusing a transport network (e.g., a transport server and associatedtransport link(s)).

The group encryption key is then transmitted to the first and secondcommunication nodes (e.g., through control channels) (operation 504).The first and second communication nodes may then exchange securecommunications.

FIG. 6 illustrates two or more exemplary systems 600 for personalcommunication nodes, such as personal communication node 601. Personalcommunication node 601 is an example of or can be part of personalcommunication nodes 102 and 103; however, personal communication node601 may have alternative configurations and methods of operation.Example 1 comprises node 601 and wireless communication device 614.Wireless communication device 614 may comprise a smartphone, tabletdevice, computer, gaming device, laptop computer, or some othercommunication device capable of communicating using packet networks orsome other communication network. Example 2 illustrates personalcommunication node software within an operating environment of anelectronic device, wherein the electronic device may comprise asmartphone, tablet device, computer, gaming device, laptop computer, orsome other communication device capable of communicating using packetnetworks or some other communication network, running a personalcommunication node software application that comprises personalcommunication node 601.

In the non-limiting example of Example 1, node 601 further comprisesprocessing system 602 and communication interface system 610. Processingsystem 602 further comprises processing circuitry 604 and storage system606. Processing circuitry 604 comprises microprocessors and othercircuitry that retrieves and executes software 608 from storage system606. Processing circuitry 604 may comprise a single device or could bedistributed across multiple devices—including devices in differentgeographic areas. Processing circuitry 604 may be embedded in varioustypes of equipment.

Storage system 606 comprises a non-transitory computer readable storagemedium, such as a disk drive, flash drive, data storage circuitry, orsome other hardware memory apparatus. Storage system 606 may comprise asingle device or could be distributed across multiple devices—includingdevices in different geographic areas. Storage system 606 may beembedded in various types of equipment. In some examples, a computerapparatus could comprise processing circuitry 604, storage system 606and software 608. Software 608 comprises attributes module 620 andconnection module 622. In addition, software 608 may include operatingsystems, utilities, drivers, network interfaces, applications, or someother type of software.

Attributes module 620 monitors one or more attributes of personalcommunication node 601 (e.g., periodically transferring a message fordelivery to a management system indicating dynamic changes in the one ormore attributes). Personal communication node 601 may comprise attributesensors such as transceivers, speakers, microphones, processing systems,communication interfaces, environmental sensors, accelerometers,gyroscopes, Global Positioning System (GPS) receivers, user interfacesand other systems to monitor various attributes and providecommunications to a remote management system. Attributes module 620 mayperiodically or continuously monitor attribute sensors or attributesensors may send an interrupt to attributes module 620 when a change isdetected.

Connection module 622 can receive instructions from a remote managementsystem regarding the formation, modification, and removal of groups(e.g., communicating with the remote management system via controlchannels and/or management communication links). It also can control theconnection of node 601 with other communication nodes for variouscommunication functions.

Encryption module 624 stores device and group encryption keys and usesthese keys to encrypt and decrypt data transferred between node 601 andone or more additional communication nodes and/or external storage forlater retrieval. A device key may be placed in encryption module 624 atthe time of manufacture of communication node 601 (or one or morecomponents of node 601).

Communication interface system 610 further comprises transceiver 612 forcommunicating with wireless communication device 614. Transceiver 612comprises communication components, such as ports, signal processingcircuitry, memory, software, and the like. Transceiver 612 communicateswith wireless communication device 614 over a link that may comprise aBluetooth communication link, WiFi link, infrared, ultrasonic or anyother communication link between personal communication node 601 andwireless communication device 614.

In the non-limiting example of Example 2, node 601 may comprise aprocessing system further comprising processing circuitry and a storagesystem. Processing circuitry may comprise microprocessors and othercircuitry that retrieves and executes software 608. Processing circuitrymay comprise a single device or could be distributed across multipledevices—including devices in different geographic areas. Processingcircuitry may be embedded in various types of equipment. Node 601 mayalso comprise a storage system further comprising a non-transitorycomputer readable storage medium, such as a disk drive, flash drive,data storage circuitry, or some other hardware memory apparatus. Thestorage system may comprise a single device or could be distributedacross multiple devices—including devices in different geographic areas.The storage system may be embedded in various types of equipment.

Node 601 further comprises software 608 including attributes module 620,connection module 622 and encryption module 624. In addition, software608 may include operating systems, utilities, drivers, networkinterfaces, applications, or some other type of software. Attributesmodule 620 can monitor one or more attributes of personal communicationnode 601 (e.g., periodically transferring a message for delivery to amanagement system indicating dynamic changes in one or more attributes).

Connection module 622 can control connection of node 601 with a remotemanagement system (e.g., receiving instructions from a remote managementsystem regarding the formation, modification, and removal of groups aswell as transmitting and receiving encryption/decryption keys and othercryptographic data). Module 622 also can control the connection of node601 with other communication nodes for various communication functions.

Encryption module 624 stores device and group encryption keys and usesthese keys to encrypt and decrypt data for transfer to othercommunication nodes or to external storage for later retrieval by othercommunication nodes. A device key may be placed in encryption module 624at the time of manufacture of communication node 602.

The included descriptions and figures depict specific embodiments toteach those skilled in the art how to make and use the best mode. Forthe purpose of teaching inventive principles, some conventional aspectshave been simplified or omitted. Those skilled in the art willappreciate variations from these embodiments that fall within the scopeof the invention. Those skilled in the art will also appreciate that thefeatures described above may be combined in various ways to formmultiple embodiments. As a result, the invention is not limited to thespecific embodiments described above, but only by the claims and theirequivalents.

What is claimed is:
 1. A method of operating a remote management system,the method comprising: receiving a request from a first communicationnode to enable secure communications between the first communicationnode and a second communication node; generating a group encryption keybased on the received request; and transferring the group encryption keyto the first and second communication nodes through one or more controlchannels.
 2. The method of claim 1 wherein the request comprisesidentity data identifying a communication group to which the first andsecond communication nodes belong.
 3. The method of claim 1 wherein therequest comprises identity data identifying the first communicationnode.
 4. The method of claim 3 wherein the identity data comprises afirst communication node device key.
 5. The method of claim 4 whereinthe first communication node device key is an ephemeral device keynegotiated by the remote management system and the first communicationnode.
 6. The method of claim 1 further comprising encrypting the groupencryption key prior to transferring the group encryption key to thefirst and second communication nodes through one or more controlchannels.
 7. The method of claim 1 wherein the group encryption key is asymmetric key.
 8. A remote management system for managing groupcommunications among communication nodes, the system comprising: one ormore processors; a computer readable storage medium having instructionsstored thereon that, when executed by the one or more processors, causethe management system to: receive a request from a first communicationnode to enable secure communications between the first communicationnode and a second communication node; generate a group encryption keybased on the received request; and transfer the group encryption key tothe first and second communication nodes through one or more controlchannels.
 9. The system of claim 8 wherein the request comprisesidentity data identifying a communication group to which the first andsecond communication nodes belong.
 10. The system of claim 8 wherein therequest comprises identity data identifying the first communicationnode.
 11. The system of claim 10 wherein the identity data comprises afirst communication node device key.
 12. The system of claim 11 whereinthe first communication node device key is an ephemeral device keynegotiated by the remote management system and the first communicationnode.
 13. The system of claim 8 wherein the instructions further causethe management system to encrypt the group encryption key prior totransferring the group encryption key to the first and secondcommunication nodes through one or more control channels.
 14. The systemof claim 8 wherein the group encryption key is a symmetric key.
 15. Amethod of operating a first communication node in a group communicationsystem, the method comprising: transmitting a request to a remotemanagement system through one or more control channels to enable securecommunications between the first communication node and a secondcommunication node; receiving a group encryption key from the remotemanagement system based on the received request; ands encrypting userdata using the group encryption key; and transmitting the encrypted userdata through a data transport network to the second communication node.16. The method of claim 15 wherein the request comprises at least one ofthe following: identity data identifying a communication group to whichthe first and second communication nodes belong; identity dataidentifying the first communication node; and/or identity datacomprising a first communication node device key.
 17. The method ofclaim 16 wherein the first communication node device key is an ephemeraldevice key negotiated by the remote management system and the firstcommunication node.
 18. The method of claim 15 further comprisingdecrypting the group encryption key prior to transferring the groupencryption key to the first and second communication nodes through oneor more control channels.
 19. The method of claim 15 wherein the groupencryption key is a symmetric key.
 20. The method of claim 1 wherein thefirst and second communication nodes exchange the secure communicationsto the exclusion of eavesdropping by the remote management system.